Skip to content

feat: ui for device transfer#805

Open
jona159 wants to merge 4 commits intodevfrom
feat/transfer-device-ui
Open

feat: ui for device transfer#805
jona159 wants to merge 4 commits intodevfrom
feat/transfer-device-ui

Conversation

@jona159
Copy link
Contributor

@jona159 jona159 commented Mar 6, 2026

Type of Change

  • Dependency upgrade
  • Bug fix (non-breaking change)
  • Breaking change
    • e.g. a fixed bug or new feature that may break something else
  • New feature
  • Code quality improvements
    • e.g. refactoring, documentation, tests, tooling, ...

Implementation

Checklist

  • I gave this pull request a meaningful title
  • My pull request is targeting the dev branch
  • I have added documentation to my code
  • I have deleted code that I have commented out

Additional Information

  • This PR closes #

@jona159 jona159 marked this pull request as ready for review March 9, 2026 08:30
@github-actions
Copy link

github-actions bot commented Mar 9, 2026

Coverage Report

Status Category Percentage Covered / Total
🔵 Lines 71.55% 1665 / 2327
🔵 Statements 69.87% 1742 / 2493
🔵 Functions 73.16% 338 / 462
🔵 Branches 58.58% 921 / 1572
File Coverage
File Stmts Branches Functions Lines Uncovered Lines
Changed Files
app/models/transfer.server.ts 76.31% 57.14% 63.63% 78.37% 21, 42, 53-54, 71, 84, 104, 113-119
Generated in workflow #2143 for commit 5e51447 by the Vitest Coverage Report Action

@jona159 jona159 changed the title feat(wip): ui for device transfer feat: ui for device transfer Mar 9, 2026
@zven zven linked an issue Mar 9, 2026 that may be closed by this pull request
{new Date(transferExpiresAt).toLocaleString()}
</b>
</p>
) : null}
Copy link
Member

@zven zven Mar 9, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Translations are missing here. Or are those only error messages? We could stick to English, then.
  • More important: Once a transfer token is created after clicking on I understand, transfer this device., it is copied to my clipboard. If I click the button again, the token not shown anymore and there is no way of retrieving it. I also can't create a new one and only get the error message Transfer already exists for this device. Result: I can never re-create a transfer token as long as an old one is valid.

return data<ActionData>(
{
success: true,
message: 'Box successfully prepared for transfer',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Didn't we want to replace the term box with device?

ns="device-transfer"
values={{ deviceName }}
components={{ b: <b /> }}
/>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't we already have the same text and information above? Duplicate!

<input
name="token"
type="text"
placeholder="Transfer-Token eingeben"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

translation missing

<div className="mt-3 rounded-md border border-green-200 bg-green-50 px-3 py-2 text-sm text-green-700">
{actionData.message ?? t('device_successfully_claimed')}
</div>
) : null}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about putting the "Gerät übernehmen" box below the devices table?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

implement transfer ui

2 participants